Data relationships in the SBO
In a SmartContainer, you can create a new SBO in the AppBuilder and drop one or more SDOs selected from the Palette. The SBO is only a static object in Progress Dynamics Version 1, so you always create it and add SDOs to it in the AppBuilder. The data links you make between SDOs in the SBO at design time determine the default order of initialization and update of the objects, but none of the objects are visualized when you run the application. Management of the SDOs by the SBO is done through the Container link, created automatically the same as for SmartWindows and Progress SmartFrames™. So all of the SDOs inside an SBO are its Container-Targets.
If there are multiple SDOs in the SBO, you must connect them to each other by Data links. You must define one of the SDOs as the master SDO. This SDO has no Data-Source. You must link all the other SDOs to it, directly or indirectly, in a Data link hierarchy, as shown in the example in Figure 11–5.
The SBO property ContainedDataObjects holds a list of all of the SDO procedure handles. The order of these handles is top-down. In the case where multiple SDOs are Data-Targets of a single parent SDO, the order will default arbitrarily. The order can be adjusted in the SBO Instance Property dialog box, so that updates to one SDO, which are dependent on updates to another (using a newly generated key value to assign to a field in a dependent SDO, for example), can be assured to happen in the correct sequence. The user-adjusted order will be saved in the UpdateOrder property.